resources/cafe-split/paths/menu.yaml:14

• This parameter item combines $ref with sibling fields (description, example). In OpenAPI/JSON Reference, siblings to $ref are not allowed and may be ignored, so the endpoint-specific docs might not apply.

Consider inlining the full Parameter object here, or creating endpoint-specific parameter components to reference instead of overriding a $ref.

    - $ref: ../components/parameters/Sort.yaml
      description: |-
        Sorts the collection by a single field. Prefix with `-` for descending order
        (for example, `-price`); omit the prefix for ascending order (`price`).

resources/cafe-split/paths/order-items.yaml:20

• This parameter item uses $ref together with sibling fields (required, description, example). $ref objects cannot have siblings, so these fields may be ignored and the spec can become invalid.

Inline the filter Parameter object here (with the orderId-only description), or create a dedicated parameter component for this endpoint and reference that.

    - $ref: ../components/parameters/Filter.yaml
      required: true
      description: |-
        Selects the order whose items to return, using a single `orderId:<value>` pair
        (for example, `orderId:ord_01h1s5z6vf2mm1mz3hevnn9va7`).

        This filter is required and only the `orderId` field is supported.
      example: orderId:ord_01h1s5z6vf2mm1mz3hevnn9va7

resources/cafe.yaml:45

• OpenAPI $ref objects must not have sibling fields (like description/example). With the current structure, these per-endpoint docs are invalid and may be ignored by tooling/resolvers.

To keep endpoint-specific docs, replace these $ref entries with full inline Parameter objects, or create endpoint-specific components/parameters/* variants (e.g. MenuSort, OrdersFilter) and reference those instead.

        - $ref: '#/components/parameters/Sort'
          description: >-
            Sorts the collection by a single field. Prefix with `-` for

tests/e2e/respect/server-override-with-console-parameters/server-override-with-console-parameters.test.ts:11

• The menu-from-cafe-api=... override looks misleading here: server overrides are applied by the OpenAPI source description name used to resolve the operation (e.g. cafe-api), and the child workflow’s OpenAPI source is also named cafe-api (in cafe-menu.arazzo.yaml). As a result, menu-from-cafe-api won’t affect request URLs, and both workflows are effectively controlled by the cafe-api override.

Either drop the unused override, or (if the intent is to test distinct overrides) rename the nested OpenAPI source in cafe-menu.arazzo.yaml and override that name instead.
resources/cafe-split/paths/orders.yaml:15

• $ref entries in parameter arrays must not be extended with sibling keys (description, example). As written, these overrides are invalid and may be ignored by OpenAPI tooling.

To keep per-endpoint docs, inline the parameter object(s) here or add dedicated components/parameters variants for orders.

    - $ref: ../components/parameters/Filter.yaml
      description: |-
        Filters the collection items using space-separated `field:value` pairs.

        **Filterable fields:** `customerName`, `status`, `totalPrice`, `createdAt`, `id`

resources/cafe.yaml:526

• This parameter also combines $ref with sibling fields (required, description, example). Per the OpenAPI Reference Object rules, those siblings may be ignored or rejected by strict tooling, which is especially risky here because required: true may not take effect.

Prefer defining an explicit parameter object here (or an endpoint-specific component like OrderItemsFilter) instead of trying to override a $ref inline.

        - $ref: '#/components/parameters/Filter'
          required: true
          description: >-
            Selects the order whose items to return, using a single
            `orderId:<value>` pair

            (for example, `orderId:ord_01h1s5z6vf2mm1mz3hevnn9va7`).


            This filter is required and only the `orderId` field is supported.
          example: orderId:ord_01h1s5z6vf2mm1mz3hevnn9va7

resources/cafe.yaml:54

• The parameter entry combines a $ref with sibling fields (description/example). In OpenAPI, a Reference Object must contain only $ref, so these siblings can be ignored by tooling or rejected by validators, and the endpoint-specific docs may not render as intended.

Consider replacing these with dedicated endpoint-specific parameter components (e.g., MenuSort, OrdersSort, etc.) or inlining full Parameter Objects instead of $ref+overrides (this pattern repeats for Filter/Search below and in other paths).

This issue also appears on line 516 of the same file.

        - $ref: '#/components/parameters/After'
        - $ref: '#/components/parameters/Before'
        - $ref: '#/components/parameters/Sort'
          description: >-
            Sorts the collection by a single field. Prefix with `-` for
            descending order

            (for example, `-price`); omit the prefix for ascending order
            (`price`).


            **Sortable fields:** `name`, `price`, `createdAt`, `updatedAt`, `id`
          example: '-price'
        - $ref: '#/components/parameters/Filter'

resources/cafe-split/paths/menu.yaml:17

• These path-level parameters attempt to override $ref-d parameter components by adding sibling description/example fields. In OpenAPI, a $ref parameter is a Reference Object (must contain only $ref), so the overrides may be ignored or rejected by validators.

To keep endpoint-specific sortable/filterable/searchable field lists, use separate parameter component files (e.g., MenuSort.yaml, MenuFilter.yaml, MenuSearch.yaml) or inline full Parameter Objects here.

    - $ref: ../components/parameters/After.yaml
    - $ref: ../components/parameters/Before.yaml
    - $ref: ../components/parameters/Sort.yaml
      description: |-
        Sorts the collection by a single field. Prefix with `-` for descending order
        (for example, `-price`); omit the prefix for ascending order (`price`).

        **Sortable fields:** `name`, `price`, `createdAt`, `updatedAt`, `id`
      example: '-price'

resources/cafe-split/paths/orders.yaml:37

• Same issue here: $ref-d parameter objects are given sibling description/example fields. OpenAPI Reference Objects should not include siblings, so these endpoint-specific docs may not be applied by tooling.

Prefer endpoint-specific parameter components (e.g., OrdersFilter.yaml, OrdersSort.yaml, OrdersSearch.yaml) or inline Parameter Objects without $ref.

    - $ref: ../components/parameters/Filter.yaml
      description: |-
        Filters the collection items using space-separated `field:value` pairs.

        **Filterable fields:** `customerName`, `status`, `totalPrice`, `createdAt`, `id`

        **Format:** `field1:value1 field2:value2`

        **Supported operators:**
        - `field:value` - Exact match
        - `field:value1,value2` - Match any of the comma-separated values (OR)
        - Time ranges (on `createdAt`): Use `30d` (30 days), `7d` (7 days), `1h` (1 hour), etc.

        **Examples:**
        - `status:placed` - Filter by a single status.
        - `status:placed,completed` - Filter by multiple statuses.
        - `createdAt:30d` - Orders created in the last 30 days.
        - `id:ord_01h1s5z6vf2mm1mz3hevnn9va7` - Filter by a specific order ID.
        - `status:placed createdAt:7d` - Combine multiple filters.
      example: status:placed
    - $ref: ../components/parameters/Sort.yaml
      description: |-
        Sorts the collection by a single field. Prefix with `-` for descending order
        (for example, `-createdAt`); omit the prefix for ascending order (`createdAt`).

        **Sortable fields:** `customerName`, `status`, `totalPrice`, `createdAt`, `updatedAt`, `id`
      example: '-createdAt'

resources/cafe-split/paths/order-items.yaml:20

• This required filter parameter is expressed as $ref plus sibling fields (required, description, example). With strict OpenAPI reference handling, those siblings can be ignored, meaning the parameter might not be required and the specialized docs might be dropped.

Prefer an explicit Parameter Object here (or an endpoint-specific component parameter) rather than overriding a $ref inline.

    - $ref: ../components/parameters/Filter.yaml
      required: true
      description: |-
        Selects the order whose items to return, using a single `orderId:<value>` pair
        (for example, `orderId:ord_01h1s5z6vf2mm1mz3hevnn9va7`).

        This filter is required and only the `orderId` field is supported.
      example: orderId:ord_01h1s5z6vf2mm1mz3hevnn9va7